sing-box: Persist user data #7572
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Support persistence for config.json, cache.db, and config directories. - Improve checkver regex and autoupdate URL for reliability.
Contributor
|
All changes look good. Wait for review from human collaborators. sing-box
|
z-Fng
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improved the sing-box manifest with proper persistence and robust update logic.
Persistence: Added
config.json,cache.db, andconfig.d/config/folder to the persist field.Initialization: Added a
pre_installscript to:$persist_direxists (fixes directory missing errors in PowerShell).config.jsonwith UTF-8 (No BOM) and LF to prevent JSON parsing errors on the first run.cache.dbfile.Update Logic: Optimized the checkver regex with a stable GitHub tag anchor.
Notes: Added guidance for TUN mode administrator requirements and multi-config directory usage.
Use conventional PR title:
<manifest-name[@version]|chore>: <general summary of the pull request>I have read the Contributing Guide